Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow using public subnets #119

Merged
merged 1 commit into from
Feb 21, 2024
Merged

allow using public subnets #119

merged 1 commit into from
Feb 21, 2024

Conversation

jaxxstorm
Copy link
Member

@jaxxstorm jaxxstorm commented Feb 21, 2024

Ellipsis 🚀 This PR description was created by Ellipsis for commit e0e7a02.

Summary:

This PR adds support for using public subnets for the bastion by introducing a new public argument to BastionArgs, updating the NewBastion function, example, schema.yaml, and SDKs accordingly.

Key points:

  • Added public argument to BastionArgs in multiple languages.
  • Updated NewBastion function to open UDP port if public is true.
  • Updated example to use public subnets.
  • Updated schema.yaml and SDKs to reflect changes.

Generated with ❤️ by ellipsis.dev

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Reviewed entire PR up to commit ecf1e2a

Reviewed 290 lines of code across 7 files in 1 minute(s) and 48 second(s).

See details
  • Skipped files: 0
  • Confidence threshold: 50%
  • Drafted 1 additional comments.
  • Workflow ID: wflow_RoYOAbDww8pe3Onh
View 1 draft comments

These comments were drafted by Ellipsis, but were filtered out of the final review. They're included here so you can see our internal thought process and help you configure your ellipsis.yaml.

Drafted 1 comments under confidence threshold

Filtered comment at provider/pkg/provider/aws/bastion.go:187

Notes: The PR is adding the ability to use public subnets for the bastion host. It adds a new 'public' argument to the BastionArgs class and uses it to conditionally open a UDP port in the security group and associate a public IP address with the bastion host. The changes look correct and follow best practices. However, the PR does not include any tests to verify the new functionality.

The changes look correct, but it would be good to add tests to verify the new functionality.

Confidence changes required: 50%


Something look wrong? Tag @ellipsis-dev in a comment, or customize the ellipsis.yaml for this repository.

Generated with ❤️ by ellipsis.dev

@jaxxstorm jaxxstorm merged commit e0e7a02 into main Feb 21, 2024
11 checks passed
@jaxxstorm jaxxstorm deleted the no_derp branch February 21, 2024 21:30
Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Incremental review on commit e0e7a02

Reviewed 289 lines of code across 7 files in 2 minute(s) and 28 second(s).

See details
  • Skipped files: 0
  • Confidence threshold: 50%
  • Drafted 1 additional comments.
  • Workflow ID: wflow_TnwcB307aUEACUXU
View 1 draft comments

These comments were drafted by Ellipsis, but were filtered out of the final review. They're included here so you can see our internal thought process and help you configure your ellipsis.yaml.

Drafted 1 comments under confidence threshold

Filtered comment at provider/pkg/provider/aws/bastion.go:33

Notes: The PR seems to be well implemented. The author has added a new argument 'public' to the BastionArgs struct in the bastion.go file. This argument is used to determine whether the bastion is going in public subnets. If it is, the UDP port is opened to ensure that DERP relays are not used. This change is reflected in all the language SDKs (Python, Node.js, .NET, and Go). The example has also been updated to use public subnets. I don't see any clear violations of best practices, logical bugs, performance bugs, or security bugs.

The implementation of the 'public' argument in the BastionArgs struct and its usage in the NewBastion function looks correct. Good job on updating the example and all the language SDKs to reflect this change.

Confidence changes required: 10%


Something look wrong? Tag @ellipsis-dev in a comment, or customize the ellipsis.yaml for this repository.

Generated with ❤️ by ellipsis.dev

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Incremental review on commit e0e7a02

Reviewed 289 lines of code across 7 files in 2 minute(s) and 21 second(s).

See details
  • Skipped files: 0
  • Confidence threshold: 50%
  • Drafted 1 additional comments.
  • Workflow ID: wflow_EOIS00qbMy5qqRjK
View 1 draft comments

These comments were drafted by Ellipsis, but were filtered out of the final review. They're included here so you can see our internal thought process and help you configure your ellipsis.yaml.

Drafted 1 comments under confidence threshold

Filtered comment at provider/pkg/provider/aws/bastion.go:187

Notes: The PR seems to be well implemented. The author has added a new argument 'public' to the BastionArgs struct in multiple languages. This argument is then used in the NewBastion function to determine whether to open the UDP port or not. The author has also updated the example to use public subnets. I don't see any clear violations of best practices, logical bugs, performance bugs, or security bugs. The code is clean and well-structured.

The implementation of the 'public' argument in the NewBastion function looks good. It correctly opens the UDP port when 'public' is true.

Confidence changes required: 10%


Something look wrong? Tag @ellipsis-dev in a comment, or customize the ellipsis.yaml for this repository.

Generated with ❤️ by ellipsis.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant